v21.0.3

Compare Source

compiler-cli

core

forms

http

router

v21.0.2

Compare Source

compiler

v21.0.1

Compare Source

compiler-cli

core

forms

http

migrations

v21.0.0

Compare Source

Blog post "Announcing Angular v21".

Breaking Changes

common

• (test only) - TestBed now provides a fake PlatformLocation
  implementation that supports the Navigation API. This may break some
  tests, though we have not observed any failures internally. You can revert to the
  old default for TestBed by providing the MockPlatformLocation from
  @angular/common/testing in your providers:
  {provide: PlatformLocation, useClass: MockPlatformLocation}
• ngComponentOutletContent is now of type Node[][] | undefined instead of any[][] | undefined.
• NgModuleFactory has been removed, use NgModule instead.

compiler-cli

• • Previously hidden type issues in host bindings may show up in your builds. Either resolve the type issues or set "typeCheckHostBindings": false in the angularCompilerOptions section of your tsconfig.
• The Angular compiler now produces an error when the
  the emitDeclarationOnly TS compiler option is enabled as this mode is
  not supported.

core

• The server-side bootstrapping process has been changed to eliminate the reliance on a global platform injector.

  Before:

  const bootstrap = () => bootstrapApplication(AppComponent, config);

  After:

  const bootstrap = (context: BootstrapContext) =>
    bootstrapApplication(AppComponent, config, context);

  A schematic is provided to automatically update main.server.ts files to pass the BootstrapContext to the bootstrapApplication call.

  In addition, getPlatform() and destroyPlatform() will now return null and be a no-op respectively when running in a server environment.

• Using a combination of provideZoneChangeDetection
  while also removing ZoneJS polyfills will no longer result in the
  internal scheduler being disabled. All Angular applications now
  consistenly use the same scheduler, and those with the Zone change detection
  provider include additional automatic scheduling behaviors based on
  NgZone stabilization.

• • TypeScript versions less than 5.9 are no longer supported.

• (test only) - Using provideZoneChangeDetection in the
  TestBed providers would previously prevent TestBed from rethrowing
  errors as it should. Errors in the test will now be rethrown, regardless
  of the usage of provideZoneChangeDetection. Tests should be adjusted to
  prevent or account for these errors. As in previous major versions,
  this behavior can be disabled with rethrowApplicationErrors: false in
  configureTestingModule as a last resort.

• ignoreChangesOutsideZone is no longer available as an
  option for configuring ZoneJS change detection behavior.

• Angular no longer provides a change detection scheduler
  for ZoneJS-based change detection by default. Add
  provideZoneChangeDetection to the providers of your
  bootstrapApplication function or your AppModule (if using
  bootstrapModule). This provider addition will be covered by an
  automated migration.

• moduleId was removed from Component metadata.

• The interpolation option on Components has been removed. Only the default {{ ... }} is now supported.

elements

• Fix signal input getter behavior in custom elements.

  Before this change, signal inputs in custom elements required function calls to access their values (elementRef.newInput()), while decorator inputs were accessed directly (elementRef.oldInput). This inconsistency caused confusion and typing difficulties.

  The getter behavior has been standardized so signal inputs can now be accessed directly, matching the behavior of decorator inputs:

  Before:

  • Decorator Input: elementRef.oldInput
  • Signal Input: elementRef.newInput()

  After:

  • Decorator Input: elementRef.oldInput
  • Signal Input: elementRef.newInput

forms

• This new directive will conflict with existing FormArray directives or formArray inputs on the same element.

platform-browser

• The deprecated ApplicationConfig export from @angular/platform-browser has been removed.
  Please import ApplicationConfig from @angular/core instead.

router

• lastSuccessfulNavigation is now a signal and needs to be invoked
• Router navigations may take several additional
  microtasks to complete. Tests have been found to often be highly
  dependent on the exact timing of navigation completions with respect to
  the microtask queue. The most common fix for tests is to ensure all
  navigations have been completed before making assertions. On rare
  occasions, this can also affect production applications. This can be
  caused by multiple subscriptions to router state throughout the application,
  both of which trigger navigations that happened to not conflict with the
  previous timing.

upgrade

• UpgradeAdapter is no longer available. Use
  upgrade/static instead

zone.js

• IE/Non-Chromium Edge are not supported anymore.

Deprecations

http

• HttpResponseBase.statusText is deprecated

common

compiler

compiler-cli

core

elements

forms

http

language-server

language-service

migrations

platform-browser

router

upgrade

v20.3.15

Compare Source

compiler

v20.3.14

Compare Source

http

v20.3.13

Compare Source

v20.3.12

Compare Source

v20.3.11

Compare Source

common

compiler

core

v20.3.10

Compare Source

compiler-cli

Commit	Description
	make required inputs diagnostic less noisy

migrations

Commit	Description
	Prevent removal of templates referenced with preceding whitespace characters

v20.3.9

Compare Source

v20.3.7

Compare Source

animations

compiler

compiler-cli

core

router

v20.3.6

Compare Source

core

platform-browser

v20.3.5

Compare Source

compiler-cli

core